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

Add WorkflowRegistry to config #15280

Conversation

cedric-cordenier
Copy link
Contributor

@cedric-cordenier cedric-cordenier commented Nov 18, 2024

Add config options to configure the WorkflowRegistry.

@cedric-cordenier cedric-cordenier force-pushed the CAPPL-136-add-workflow-registry-syncer-config-options branch from 5229d20 to 13802d1 Compare November 18, 2024 13:16
Copy link
Contributor

github-actions bot commented Nov 18, 2024

AER Report: CI Core ran successfully ✅

aer_workflow , commit

AER Report: Operator UI CI ran successfully ✅

aer_workflow , commit

@cedric-cordenier cedric-cordenier force-pushed the CAPPL-136-add-workflow-registry-syncer-config-options branch 4 times, most recently from 20d758d to c9ad88b Compare November 19, 2024 11:33
@cedric-cordenier cedric-cordenier force-pushed the CAPPL-136-add-workflow-registry-syncer-config-options branch from e11a776 to bb53d8b Compare November 20, 2024 11:58
@cedric-cordenier cedric-cordenier marked this pull request as ready for review November 20, 2024 12:35
@cedric-cordenier cedric-cordenier requested review from a team as code owners November 20, 2024 12:35
@cedric-cordenier cedric-cordenier added this pull request to the merge queue Nov 20, 2024
Merged via the queue into develop with commit 2ea3aef Nov 20, 2024
145 of 146 checks passed
@cedric-cordenier cedric-cordenier deleted the CAPPL-136-add-workflow-registry-syncer-config-options branch November 20, 2024 13:32
@@ -279,6 +279,11 @@ Address = ''
NetworkID = 'evm'
ChainID = '1'

[Capabilities.WorkflowRegistry]
Address = ''
Copy link
Contributor

Choose a reason for hiding this comment

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

@cedric-cordenier, does config-full imply empty values?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

It just means that all values have been set explicitly

```toml
NetworkID = 'evm' # Default
```
NetworkID identifies the target network where the remote registry is located.
Copy link
Contributor

Choose a reason for hiding this comment

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

Could you list the other examples of the NetworkID values here as well?

ChainID *string
}

func (r *WorkflowRegistry) setFrom(f *WorkflowRegistry) {
Copy link
Contributor

Choose a reason for hiding this comment

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

Would an unset or empty field invalidate the node's config on boot if the WorkflowRegistry is defined in the config but is missing a field or value?
Please reflect it (the invalid configuration) in your test data/scripts by showing what would be an invalid way of setting the config.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

No, these are optional values so they can be unset.

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.

5 participants