Skip to content
This repository has been archived by the owner on Oct 30, 2018. It is now read-only.

Pull SSL certificate IDs from existing ELBs #22

Merged
merged 1 commit into from
Feb 16, 2015
Merged

Pull SSL certificate IDs from existing ELBs #22

merged 1 commit into from
Feb 16, 2015

Conversation

teamdoug
Copy link
Contributor

Fixes ansible/ansible#9073 and fixes #22
The root cause of that issue is that boto's "get_complex_tuple()" doesn't include the ssl_certificate_id for some unknown reason. I'm following up on this upstream, but a workaround for now would be nice :)

@bcoca
Copy link
Member

bcoca commented Jan 21, 2015

Rebase Request

Hi!

Thanks very much for your submission to Ansible. It sincerely means a lot to us.

It looks like the code underneath has changed since this was submitted. Can you take care of rebasing this for us?

  • You should be able to run "git rebase" against this branch to bring it up to date
  • Resolve any merge conflicts and test changes
  • Push to the same branch and github should update the pull request automatically.

Just as a quick reminder of things, this is a really busy project. We have over 800 contributors and to manage the queue effectively
we assign things a priority between P1 (highest) and P5. We'd like to thank you very much for your time!
We'll work things in priority order, so just wanted you to be aware of the queue and know we haven't forgotten about you!

We will definitely see your comments on this issue when reading this ticket, but may not be able to reply promptly. You may also wish to join one of our two mailing lists
which are very active:

Thank you once again for this and your interest in Ansible!

@endzyme
Copy link

endzyme commented Feb 4, 2015

Poke

bcoca added a commit that referenced this pull request Feb 16, 2015
Pull SSL certificate IDs from existing ELBs
@bcoca bcoca merged commit 6c4804e into ansible:devel Feb 16, 2015
@juliedavila
Copy link
Contributor

fixes #23

@endzyme
Copy link

endzyme commented Mar 23, 2015

Thanks!!!

@hackndoes
Copy link

hackndoes commented Jun 22, 2017

I am on ansible 2.2.0.0 and it still happens to me.
here is my code:

ec2_elb_lb:
    name: "name"
    region: '{{ region }}'
    state: present
    subnets: "{{ subnet_list }}"
    instance_ids: "{{ instance_id_list }}"
    security_group_names: [group1, group2]
    scheme: "internet-facing"
    cross_az_load_balancing: yes
    wait: yes
    tags:
      Name: "name"
      environment: '{{ env }}'
    stickiness:
      type: "{{ sticki_type}}"
      enabled: "{{ sticki_enabled }}"
      expiration: "{{ sticki_expiration }}"

    health_check:
      ping_protocol: "https"
      ping_port: "443"
      ping_path: "/"
      response_timeout: "300"
      interval: "5"
      unhealthy_threshold: "10"
      healthy_threshold: "3"

    listeners:
      - protocol: https
        load_balancer_port: 443
        instance_protocol: "8080"
        instance_port: "{{ item.instance_port }}"
        # proxy_protocol: True
        ssl_certificate_id: "{{ ssl_certificate_arn }}"

@willthames
Copy link
Contributor

Please raise a new issue in ansible/ansible. This repo is no longer used, and this PR is closed.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

ec2_elb_lb always reports a changed state when specifying a https listener with certificate
7 participants