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

feat: ACNA-1602 - add new flag to prevent action code deployment #537

Conversation

arjuncooliitr
Copy link
Contributor

@arjuncooliitr arjuncooliitr commented May 27, 2022

Description

--[no-]action-code flag added to the aio-cli-plugin-app deploy command to prevent action code deployment

Pre-requisite

Related Issue

Closes #538

Motivation and Context

How Has This Been Tested?

Screenshots (if appropriate):

Types of changes

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to change)

Checklist:

  • I have signed the Adobe Open Source CLA.
  • My code follows the code style of this project.
  • My change requires a change to the documentation.
  • I have updated the documentation accordingly.
  • I have read the CONTRIBUTING document.
  • I have added tests to cover my changes.
  • All new and existing tests passed.

README.md Outdated Show resolved Hide resolved
src/commands/app/deploy.js Outdated Show resolved Hide resolved
@shazron shazron changed the title Added new flag to prevent action code deployment feat: add new flag to prevent action code deployment May 30, 2022
@shazron shazron changed the title feat: add new flag to prevent action code deployment feat: ACNA-1602 - add new flag to prevent action code deployment May 30, 2022
Copy link
Member

@shazron shazron left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

see threaded comments for changes

@shazron
Copy link
Member

shazron commented Jun 2, 2022

@arjuncooliitr 1 unit test failure - can you fix so we can add this for a potential Monday release?

@codecov
Copy link

codecov bot commented Jun 3, 2022

Codecov Report

Merging #537 (8edab56) into master (70b9a42) will not change coverage.
The diff coverage is 100.00%.

@@            Coverage Diff            @@
##            master      #537   +/-   ##
=========================================
  Coverage   100.00%   100.00%           
=========================================
  Files           53        53           
  Lines         2812      2813    +1     
  Branches       527       527           
=========================================
+ Hits          2812      2813    +1     
Impacted Files Coverage Δ
src/commands/app/deploy.js 100.00% <100.00%> (ø)

📣 We’re building smart automated test selection to slash your CI/CD build times. Learn more

@shazron shazron marked this pull request as ready for review June 6, 2022 03:37
@purplecabbage
Copy link
Member

It looks like it, but can you verify that these are supported?

Update the params for action1 only ( assume there are many actions in the project )
aio app deploy --no-web-assets -a action1 --no-action-code

Update the params and deploy action1 only ( many actions in project )
aio app deploy --no-web-assets -a action1

@arjuncooliitr
Copy link
Contributor Author

arjuncooliitr commented Jun 22, 2022

I tried to verify using a test app builder app having 2 actions. Say action1 and action2.
Behavior of the command is as follows:

aio app deploy --no-web-assets -a action1
=> Deploys only action1 with params and code
aio app deploy --no-web-assets -a action1 --no-action-code
=> Deploys only action1 with params (doesn't pick up action code changes)

So, I think it works as desired

@shazron
Copy link
Member

shazron commented Aug 25, 2022

Update: We are still looking over semantics. Discussion and final decision needed before merging.

@shazron
Copy link
Member

shazron commented Oct 26, 2022

@arjuncooliitr can you fix up the conflict? thanks!

@arjuncooliitr
Copy link
Contributor Author

@purplecabbage Sorry this has been long overdue 😅 but you mentioned long back that you had some thoughts regarding the semantics of this flag, so we didn't merge and kept it on hold.
What are your thoughts now? If it looks okay to you then we can proceed and merge.

@arjuncooliitr
Copy link
Contributor Author

@shazron, resolved the conflict thanks!

@shazron
Copy link
Member

shazron commented Jan 30, 2023

@arjuncooliitr can you resolve the new conflict?
@purplecabbage please see Arjun's comments above so this can be resolved.

@purplecabbage
Copy link
Member

This is being closed in favor of updated documentation. This pull request was well implemented, however the convenience was deemed to potentially lead to developers overwriting actions as the command syntax was awkward.
The command aio runtime action update --param is expected to be used instead of surfacing the command as an additional flag on aio app deploy

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Feature Request - Deploy changes to secrets from .env file without deploying the entire application
4 participants