Open sfhardman opened 6 years ago
Thank you @sfhardman for the valuable comment. Could you please verify your manifests on this branch. This branch contains the temporary fix. Thanks again for your time. https://github.com/sheenaajay/puppetlabs-azure_arm/tree/fixforapplication
The updated branch gets a bit further but now errors with:
Alert: Exception during create. The state of the resource is unknown. ex is undefined method ``[]=' for nil:NilClass and backtrace is ["/tmp/vagrant-puppet/modules-0a26a273e7687a678beb88197201a9d1/azure_arm/lib/puppet/provider/azure_application/azure_application.rb:350:in ``block in add_keys_to_request'", "/tmp/vagrant-puppet/modules-0a26a273e7687a678beb88197201a9d1/azure_arm/lib/puppet/provider/azure_application/azure_application.rb:350:in ``each'"
This is because self.call_op does not handle POST requests. A fix for this is in:
@sfhardman Thanks alot for your contribution.
What you expected to happen?
Expected an Azure application registration to be created
What happened?
An error was thrown: Alert: Exception during exists_one. ex is Invalid parameter objectid(:objectid)
How to reproduce it?
Puppet manifest:
Anything else we need to know?
I can successfully provision VM and network resources as per the example in this repo. I started on fixing the issue but there looks to be quite a bit still to be done: https://github.com/sfhardman/puppetlabs-azure_arm/commit/196029f5af1011e6698dc7bef64c876745fdab0d
It would be great if you could flag which of the resources in this module are known good, and which are untested autogenerated code
Versions:
Logs: