You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When importing the emailProvider configuration and creating a custom email provider action via a0deploy import, the operation fails during the processChanges stage when processing the emailProvider type.
Expectation
The processing of the emailProvider type does not fail during a0deploy import if the required action is also created in the same import.
Workaround
To overcome this, we first create the action and then add the emailProvider configuration.
Run a0deploy import without the emailProvider property in tenant.yml. This will create the action.
Then, run a0deploy import again, this time with the emailProvider property in place. Since the action has already been created, the processing of emailProvider will no longer fail."
However, we expect this to work in a single execution.
Reproduction
1 - Given the tenant.yml configuration has the emailProvider type being enabled and the custom email provider action being created in the same import.
Problem running command import during stage processChanges when processing type emailProvider
No deployed action of type custom-email-provider was found
Deploy CLI version
7.24.2
Node version
20.14.0
The text was updated successfully, but these errors were encountered:
jeanfdmelo
changed the title
Import fails when processing the type emailProvider because it takes precedence over the creation of the required custom-email-provider action
Import fails when processing the type emailProvider and creating a custom email provider action in the same execution
Aug 29, 2024
Checklist
Description
When importing the
emailProvider
configuration and creating acustom email provider
action viaa0deploy import
, the operation fails during theprocessChanges
stage when processing theemailProvider
type.Expectation
The processing of the
emailProvider
type does not fail duringa0deploy import
if the required action is also created in the same import.Workaround
To overcome this, we first create the action and then add the
emailProvider
configuration.emailProvider
property intenant.yml
. This will create the action.emailProvider
property in place. Since the action has already been created, the processing ofemailProvider
will no longer fail."However, we expect this to work in a single execution.
Reproduction
1 - Given the
tenant.yml
configuration has theemailProvider
type being enabled and thecustom email provider
action being created in the same import.tenant.yml
2 - When import is executed
a0deploy import --input_file tenant.yaml
3 - Then command fails with the error message:
Deploy CLI version
7.24.2
Node version
20.14.0
The text was updated successfully, but these errors were encountered: