Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

DXE-2447 command >> update-local | incomplete , possible missing arguments #83

Open
tpimenta88 opened this issue Mar 8, 2023 · 2 comments
Assignees
Labels
bug Something isn't working delivery

Comments

@tpimenta88
Copy link

tpimenta88 commented Mar 8, 2023

akamai property-manager update-local -p qa.example.com

i assume that qa.example.com is the property's name inside the Property Manager in the akamai portal.
when the command is run, how does it know the environment and pipeline to update locally?
keep getting the error :
_PM CLI Error: 'property_folder_does_not_exist' occurred:
Error: Property folder 'qa.example.com' does not exist
at DevopsPropertyManager.updateProperty (/Users/xx/.akamai-cli/src/cli-property-manager/src/pm/devops_property_manager.js:162:19)
at update (/Users/xx/.akamai-cli/src/cli-property-manager/src/pm/property_manager_cli.js:698:44)
at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
Error details:
Argument #0: qa.example.com

and the reality is the folder does not exist, what we have is env>qa
in a directory structure as follows:

\example.com (pipeline name)

\cache
\dist
\env
>\qa
>\prod

so should we not have to specify the property we want to fetch and the pipeline+environment to update???
Should the command look like:
akamai property-manager update-local -p <property_name in PM> -p pipelineName <environment_name>

@tpimenta88 tpimenta88 changed the title command update-local|ul [options] command update-local -- incomplete , possible missing arguments Mar 8, 2023
@tpimenta88 tpimenta88 changed the title command update-local -- incomplete , possible missing arguments command update-local | incomplete , possible missing arguments Mar 8, 2023
@tpimenta88 tpimenta88 changed the title command update-local | incomplete , possible missing arguments command >> update-local | incomplete , possible missing arguments Mar 9, 2023
@Slonimskaia
Copy link

Hi @tpimenta88,

Thank you for raising this issue. We will reproduce it from our side and come back to you soon.

Best regards,
Tatiana

@kaush- kaush- changed the title command >> update-local | incomplete , possible missing arguments DXE-2447 command >> update-local | incomplete , possible missing arguments Mar 17, 2023
@kaush- kaush- added bug Something isn't working and removed under-investigation labels Mar 17, 2023
@tpimenta88
Copy link
Author

tpimenta88 commented Mar 17, 2023

akamai property-manager update-local -p qa.example.com

i assume that qa.example.com is the property's name inside the Property Manager in the akamai portal. when the command is run, how does it know the environment and pipeline to update locally? keep getting the error : _PM CLI Error: 'property_folder_does_not_exist' occurred: Error: Property folder 'qa.example.com' does not exist at DevopsPropertyManager.updateProperty (/Users/xx/.akamai-cli/src/cli-property-manager/src/pm/devops_property_manager.js:162:19) at update (/Users/xx/.akamai-cli/src/cli-property-manager/src/pm/property_manager_cli.js:698:44) at process.processTicksAndRejections (node:internal/process/task_queues:95:5) Error details: Argument #0: qa.example.com

and the reality is the folder does not exist, what we have is env>qa in a directory structure as follows:

\example.com (pipeline name)

\cache
\dist
\env

\qa
\prod

so should we not have to specify the property we want to fetch and the pipeline+environment to update??? Should the command look like: akamai property-manager update-local -p <property_name in PM> -p pipelineName <environment_name>
So FROM: "-p <property_name in PM>" update-local pipeline & env, the TO :"-p pipelineName <environment_name>"

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working delivery
Development

No branches or pull requests

4 participants