/charm-tools

charm build does not merge actions.yaml #82

Closed
marcoceppi opened this Issue Dec 14, 2015 · 1 comment

Comments

Assignees
No one assigned
Labels
charm-build
Projects
None yet
Milestone
  2.0
2 participants
@marcoceppi @johnsca
@marcoceppi
Owner

marcoceppi commented Dec 14, 2015

and it probably should

@marcoceppi marcoceppi added the charm-build label Dec 14, 2015

@johnsca
Member

johnsca commented Dec 14, 2015

+1 it definitely should. However, if we want full reactive action support, it should also build reactive templates for the actions using the same template it uses for hooks (see #75). For some discussion on whether we should have full reactive support for actions, see juju-solutions/charms.reactive#11

@johnsca johnsca added this to the 2.0 milestone Feb 11, 2016

johnsca added a commit to johnsca/charm-tools that referenced this issue Feb 12, 2016

@johnsca
Fixed #82: actions.yaml should be merged between layers
710064a

marcoceppi added a commit that referenced this issue Feb 12, 2016

@marcoceppi
Merge pull request #109 from johnsca/issue-82 
Fixed #82: actions.yaml should be merged between layers
119f6a5

@johnsca johnsca closed this Feb 12, 2016

marcoceppi added a commit that referenced this issue Mar 3, 2016

@johnsca @marcoceppi
Fixed #82: actions.yaml should be merged between layers
3f65d5d
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment