Skip to content

Conversation

@JoaoMacedo03
Copy link

Description

I encountered the same issue detailed in #183. While executing zcli apps:update within a GitHub action, the CLI overwrote the app configurations set by my client. I believe a straightforward flag to prevent the execution of the API endpoint /api/${product}/apps/installations/${installation_id}.json would suffice in scenarios like mine. However, I'm open to further discussion.

Do NOT write here! This section will be filled in by GitHub Action
automatically. If you don't want this, either remove the markers or write
outside the fences.

Resolves #183

Checklist

  • 💂‍♂️ includes new unit and functional tests

@JoaoMacedo03 JoaoMacedo03 requested a review from a team as a code owner September 18, 2023 19:51
@fairphone-franz-geiger
Copy link

Indeed, this would be great for using zcli in CI.

Dear code owners, how can we move this forward, so that it gets merged?

@nsehic
Copy link

nsehic commented Aug 5, 2024

Any progress on this?

@mtsolakiszen
Copy link
Contributor

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@mtsolakiszen mtsolakiszen added the wontfix This will not be worked on label Aug 1, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

wontfix This will not be worked on

Projects

None yet

Development

Successfully merging this pull request may close these issues.

apps:update sending testing settings via parameters seems like a dangerous footgun?

4 participants