April 25, 2022
We’ve released API v1.5.44 and CLI v0.11.0
Summary
API v1.5.44
-
Added environment support to the API. All management routes now accept an Environment ID and all client routes accept an Environment Name
-
All routes that do not specify an environment will default to the production environment.
-
All routes that do not have an Environment ID or Name in the path have been marked deprecated. They have not actually been deprecated and will not be removed, but we wanted to indicate to developers in the documentation which routes should be used going forward.
-
All new routes have an Operation ID with the suffix ‘Env’. This is to preserve compatibility with code generators.
-
Added direct signed URL uploads. When creating an entry to be uploaded via a signed URL you are not required to specify a content_hash or content_size.
-
Add the signed_url flag to CreateEntryEnv
-
Add the signed_url flag to UpdateEntryEnv
-
Add the signed_url flag to CreateOrUpdateEntryByPathEnv
-
Added from_environment_id, from_environment_name, to_environment_id, to_environment_name in the response of GetPromotionEnv and GetPromotionsEnv
CLI v0.11.0
-
BREAKING CHANGE: We are introducing environment support to the CLI. CLI versions less than v0.11.0 will continue to work, but once you upgrade you will now need to add the --environment flag to most commands. Example:
-
ucd buckets list --environment=[ENVIRONMENT_ID] [PROJECT_ID] -
You can also save an environment to be used in all future commands by using the config environment
-
command:
-
ucd config environment [ENVIRONMENT_ID] -
To find a list of environments for your project and their corresponding IDs visit the Dashboard. Click on Projects. Find your Project and then click on Environments under Project Settings.
-
BREAKING CHANGE: An error message in CLI has changed from “No buckets found for project.” to “No buckets found for given project and environment.”