@mattw
RE: irc discussion, yes, if you can adjust the existing action along with your new actions, that would be great.
I would bzr mv the action files to add the .py extensions, then add a symlink of the old action filename to the new .py filename.
Here is an example of this approach in different charm:
openstack_upgrade --> symlinks to --> openstack_upgrade.py
http://bazaar.launchpad.net/~openstack-charmers/charms/trusty/swift-storage/next/files/head:/actions/
Thanks again!
« Back to merge proposal
@mattw
RE: irc discussion, yes, if you can adjust the existing action along with your new actions, that would be great.
I would bzr mv the action files to add the .py extensions, then add a symlink of the old action filename to the new .py filename.
Here is an example of this approach in different charm:
openstack_upgrade --> symlinks to --> openstack_ upgrade. py
http:// bazaar. launchpad. net/~openstack- charmers/ charms/ trusty/ swift-storage/ next/files/ head:/actions/
Thanks again!