Fetch the staging version or production version, not the latest version

[maslanahi]

I could not find a way of specifying the staging or production version when importing. The only option I see is to fetch the Latest Version which may not be the version in Stage or Prod.

[SpencerMalone]

Agreed on this! Fetching a specific version or environment both for import, and for update-local are definite pre-requisites to adoption IMO.

[optplx]

Could also be extended to the property-manager show-ruletree command (so that we can for example compare local code with the production version)

[ddcrjlalumiere]

I'm definitely looking for the ability to specify an arbitrary version to import.

[akshayranganath]

We got this exact same ask from another Akamai customer yesterday. Specifically, we need the support for version number on these 3 calls:

• import
• update-local
• activate

[aetsai]

probably new-pipeline command too. documentation says it supports it but don't see it working

[ddcrjlalumiere]

Once again finding myself wishing this functionality existed :-/

[bobstrecansky]

Was wondering if there was any update on this?

[NehaGhateAkamai]

We have few commands which are available to work on user sent property version number. --help/-h will give more details .

1. akamai property-manager property-update [options]
2. akamai property-manager new-property|np [options]
3. akamai property-manager activate-version [options]
4. akamai property-manager show-ruletree|sr [options]
5. akamai property-manager hostname-update|hu [options]

If your use case is still not resolved, we would need more clarification on the use case. Is it specific to pipeline commands or property-manager commands ?

[jaescalo]

This option doesn't seem available to snippets or pipeline though. Can you confirm, or if there is a work-around? If not then will be a very useful feature.

[lkowalsk-akamai-com]

Ability to specify production/staging environment was previously added.

[ddcrjlalumiere]

Ability to specify production/staging environment was previously added.

Was it though? And most people here seem to be asking for the ability to select specific versions. According to the help output at least there does not seem to be a way to specify environment nor property version. Am I missing something?

$ akamai property-manager --version
0.7.8-RELEASE

$ akamai property-manager help update-local
Usage: akamai property-manager update-local|ul [options]

Update local property with the latest version from the Property Manager API.

Options:
  -p, --property <propertyName>   Property name. Optional if default property was set using the set-default command.
  --dry-run                       Verify the result of your command syntax before running it. Displays the JSON generated by the command as currently written.
  --force-update                  WARNING: This option bypasses the confirmation prompt and automatically overwrites your local files.
  --variable-mode <variableMode>  Choose how this command pulls in variables. Allowed values are 'no-var' and 'user-var-value'.  Default functionality is no-var.
  -h, --help                      output usage information

  © 2017-2020 Akamai Technologies, Inc. All rights reserved
  Visit http://github.com/akamai/cli-property-manager for more documentation

# Maybe there are toplevel options? Don't seem to be :-/ 
$ akamai property-manager help
Usage: akamai property-manager [options] [command]

Property Manager CLI. Run these commands from the project directory that contains your local properties.

Options:
  -V, --version                              output the version number
  -f, --format <format>                      Select output format for commands, either 'table', the default, or 'json'.
  -s, --section <section>                    The section of the .edgerc file containing the user profile, or client ID, to use for the command. If not set, uses the 'default' settings in the .edgerc file.
  -v, --verbose                              Show detailed log information for the command.
  --edgerc <edgerc>                          Optional. Enter the location of the .edgerc file used for credentials. If option not set, uses the edgerc.config file in the project directory.  Otherwise, uses the .edgerc file in your home directory.
  --workspace <workspace>                    Optional. Enter the directory containing all property and project files. If option not set, uses the value of the AKAMAI_PROJECT_HOME environment variable. Otherwise, uses the current working directory as
                                             the workspace.
  -a, --accountSwitchKey <accountSwitchKey>  Optional. If you have multiple accounts, enter the account switch key you want to use when running commands. You can use the Identity Management API to retrieve the key:
                                             https://developer.akamai.com/api/core_features/identity_management/v2.html#getaccountswitchkeys.
  -h, --help                                 output usage information

Commands:
 <SNIP commands>

  © 2017-2020 Akamai Technologies, Inc. All rights reserved
  Visit http://github.com/akamai/cli-property-manager for more documentation

[mgwoj]

Hello @ddcrjlalumiere ,

There is no need to provide expected environment when requesting specific version. Some commands support option --propver to specify version to use, see https://github.com/akamai/cli-property-manager/blob/master/docs/cli_pm_commands_help.md
If you think any other commands need this option, please list them with justification.

Thanks,
Michal

[NehaGhateAkamai]

We do provide a way in property-manager-cli, to work at environment level . It needs a pipeline setup for configs provided in this same repository. It is use-case based, please read more at https://github.com/akamai/cli-property-manager#akamai-pipeline-workflow.

[rschneider-chwy]

Can we open this issue back up? If I can clarify, the ask was to have the ability to specify versions to the update-local and import commands.

Something like:

akamai property-manager update-local -p example.com --propver 64

This would help with workflows for properties that multiple people make changes to. In the current implementation, I can make a new version in the Akamai Console as v64 but when I run update-local I could get v65 if someone creates another new version. Being able to specify --propver 64 when running update-local would fix this issue.

[ddcrjlalumiere]

@rschneider-chwy 's explanation is spot on, co-signed 🙏