Skip to content

Commit

Permalink
Update services based on release-2025-01-06 of AWS Go SDK
Browse files Browse the repository at this point in the history
  • Loading branch information
web-flow committed Jan 7, 2025
1 parent 8ac0012 commit bf7fb5d
Show file tree
Hide file tree
Showing 2 changed files with 13 additions and 15 deletions.
2 changes: 1 addition & 1 deletion .latest-tag-aws-sdk-go
Original file line number Diff line number Diff line change
@@ -1 +1 @@
release-2025-01-03
release-2025-01-06
26 changes: 12 additions & 14 deletions src/aws_supplychain.erl
Original file line number Diff line number Diff line change
Expand Up @@ -387,7 +387,8 @@
%% <<"instanceDescription">> => string(),
%% <<"instanceName">> => string(),
%% <<"kmsKeyArn">> => string(),
%% <<"tags">> => map()
%% <<"tags">> => map(),
%% <<"webAppDnsDomain">> => string()
%% }
-type create_instance_request() :: #{binary() => any()}.

Expand Down Expand Up @@ -966,9 +967,8 @@ delete_data_lake_dataset(Client, InstanceId, Name, Namespace, Input0, Options0)
%% This is an asynchronous operation. Upon receiving a DeleteInstance
%% request, Amazon Web Services Supply Chain immediately returns a response
%% with the instance resource, delete state while cleaning up all Amazon Web
%% Services resources created during
%% the instance creation process. You can use the GetInstance action to check
%% the instance status.
%% Services resources created during the instance creation process. You can
%% use the GetInstance action to check the instance status.
-spec delete_instance(aws_client:aws_client(), binary() | list(), delete_instance_request()) ->
{ok, delete_instance_response(), tuple()} |
{error, any()} |
Expand Down Expand Up @@ -1340,9 +1340,9 @@ list_tags_for_resource(Client, ResourceArn, QueryMap, HeadersMap, Options0)
%% for analysis or monitoring.
%%
%% The real-time data events are stored in an Amazon Web Services service
%% before being processed and stored in data lake.
%% New data events are synced with data lake at 5 PM GMT everyday. The
%% updated transactional data is available in data lake after ingestion.
%% before being processed and stored in data lake. New data events are synced
%% with data lake at 5 PM GMT everyday. The updated transactional data is
%% available in data lake after ingestion.
-spec send_data_integration_event(aws_client:aws_client(), binary() | list(), send_data_integration_event_request()) ->
{ok, send_data_integration_event_response(), tuple()} |
{error, any()} |
Expand Down Expand Up @@ -1380,10 +1380,9 @@ send_data_integration_event(Client, InstanceId, Input0, Options0) ->
%% instance, data flow, or dataset in AWS Supply chain.
%%
%% During the data ingestion process, you can add tags such as dev, test, or
%% prod to data flows
%% created during the data ingestion process in the AWS Supply Chain
%% datasets. You can use these tags to identify a group of resources or a
%% single resource used by the developer.
%% prod to data flows created during the data ingestion process in the AWS
%% Supply Chain datasets. You can use these tags to identify a group of
%% resources or a single resource used by the developer.
-spec tag_resource(aws_client:aws_client(), binary() | list(), tag_resource_request()) ->
{ok, tag_resource_response(), tuple()} |
{error, any()} |
Expand Down Expand Up @@ -1421,9 +1420,8 @@ tag_resource(Client, ResourceArn, Input0, Options0) ->
%% such as instance, data flow, or dataset in AWS Supply Chain.
%%
%% During the data ingestion process, you can delete tags such as dev, test,
%% or prod to data flows
%% created during the data ingestion process in the AWS Supply Chain
%% datasets.
%% or prod to data flows created during the data ingestion process in the AWS
%% Supply Chain datasets.
-spec untag_resource(aws_client:aws_client(), binary() | list(), untag_resource_request()) ->
{ok, untag_resource_response(), tuple()} |
{error, any()} |
Expand Down

0 comments on commit bf7fb5d

Please sign in to comment.