Need Guidance for Adding VPC service LWRPs in Boto Chef Cookbook


#1

Hi Friends,
I am basically working on Boto Chef Cookbook available at https://github.com/xhost-cookbooks/boto. I am trying to create custom resources and providers in order to automate various aws services. The above cookbook does it with the help of recipes which involves python script to perform the automation.

Currently, I have my own resource and my own provider for creating VPC and launching subnet, gateway, route table and network-acl all to gather in one action called create_vpc which indeed uses python script to perform those task.
I am attaching the custom resource and provider file along with the recipe.

I am facing following problems:

  1.   I am not able to access the attribute_name variable using @new.resource.attribute_name inside my python script written inside the script resource. So, I am using alternative way of accessing them by declaring new variables
    
  2.   In the Create_vpc action inside my custom provider, I am getting various attribute error such as:
    

a. Unexpected keyword argument ‘instance_tenancy’

b. VPC object has no attribute “update”

c. ‘VPCConnection’ object has no attribute ‘create_network_acl’

If anyone could help me or guide me on this it’ll be a great help :slight_smile:

Regards,
Sweeti Bharti, Software Engineer
Cybage Software Pvt. Ltd.
Phone (O): 91-20-66041700, Ext: 8447

"Legal Disclaimer: This electronic message and all contents contain information from Cybage Software Private Limited which may be privileged, confidential, or otherwise protected from disclosure. The information is intended to be for the addressee(s) only. If you are not an addressee, any disclosure, copy, distribution, or use of the contents of this message is strictly prohibited. If you have received this electronic message in error please notify the sender by reply e-mail to and destroy the original message and all copies. Cybage has taken every reasonable precaution to minimize the risk of malicious content in the mail, but is not liable for any damage you may sustain as a result of any malicious content in this e-mail. You should carry out your own malicious content checks before opening the e-mail or attachment."
www.cybage.com