Skip to content

configuration: define scope accessibility and add applicationScopes#177

Merged
hongchaodeng merged 2 commits intooam-dev:masterfrom
hongchaodeng:scope
Oct 8, 2019
Merged

configuration: define scope accessibility and add applicationScopes#177
hongchaodeng merged 2 commits intooam-dev:masterfrom
hongchaodeng:scope

Conversation

@hongchaodeng
Copy link
Copy Markdown
Member

@hongchaodeng hongchaodeng commented Oct 1, 2019

  • In the meeting, we have discussed agreed to not add new concept but reuse existing AppConfig. The idea is that AppConfig will be accessible by components from any other application configuration. This would solve the reference problem
  • The applicationScopes section is missing under component. This PR fix it.

closes https://github.com/microsoft/hydra-spec/issues/144 https://github.com/microsoft/hydra-spec/issues/130

@hongchaodeng
Copy link
Copy Markdown
Member Author

@mikkelhegn @technosophos @suhuruli @vturecek

This shall go into 1.0.0-alpha milestone and make the docs explicit.

@hongchaodeng hongchaodeng added this to the 1.0.0-alpha1 milestone Oct 1, 2019
Copy link
Copy Markdown
Member

@vturecek vturecek left a comment

Choose a reason for hiding this comment

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

LGTM

Comment on lines +342 to +358

```yaml
apiVersion: core.hydra.io/v1alpha1
kind: ApplicationConfiguration
metadata:
name: my-vpc-network
spec:
variables:
- name: networkName
value: "my-vpc"
scopes:
- name: myNetworkScope
type: core.hydra.io/v1alpha1.Network
properties:
- name: networkName
value: "[fromVariable(networkName)]"
---
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

I like this. Showing scopes in a separate app config file from the component instances is a good idea. It's a fairly intuitive solution to managing scopes and components once you see it like this.

@hongchaodeng
Copy link
Copy Markdown
Member Author

Hi @mikkelhegn
In today's meeting, we have discussed this issue again. We still have consensus on this same definition and moreover we feel it better to not break anything close to the coming release window.

Let's go ahead to make things work first. I'm very open to any future discussions. Thanks!

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.

Proposal: Instantiation of Application Scopes should not be bound to Application Configuration deployments

2 participants