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

OneFlow: multilevel user inputs #6680

Closed
3 tasks
MiguelERuiz opened this issue Jul 31, 2024 · 0 comments · Fixed by OpenNebula/docs#3080
Closed
3 tasks

OneFlow: multilevel user inputs #6680

MiguelERuiz opened this issue Jul 31, 2024 · 0 comments · Fixed by OpenNebula/docs#3080
Assignees

Comments

@MiguelERuiz
Copy link
Member

Description
One feature it is desirable to maintain the variable definition from custom attributes, so despite of the fact custom_attributes is deleted on #6679, this feature is taken on user_inputs property from oneflow-template.

Besides, not only user_inputs can be defined at rol level but also at service level. With this, we get the following advantages:

  • The possibility to create variables at rol scope
  • The possibility to create variables at service level, that could be overwritten at rol level.
  • A better control on the attributes of each rol (i.e expansion avoiding)

Use case
This feature should be useful on VRouters OneFlow declaration since we can declare variables at service scope that could be applied only for VRouters.

Interface Changes
Describe any changes you'd like to see to current interfaces including Sunstone, CLI, or/and API

Sunstone, Fireedge, CLI and OneFlow API.

Progress Status

  • Code committed
  • Testing - QA
  • Documentation (Release notes - resolved issues, compatibility, known issues)
@MiguelERuiz MiguelERuiz self-assigned this Jul 31, 2024
@vickmp vickmp self-assigned this Aug 12, 2024
@vickmp vickmp linked a pull request Oct 14, 2024 that will close this issue
1 task
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants