Splitting a single task into a role does not make much sense to me.
But if you want to go ahead with it, just pass any variables you are
currently using in your task, to the role.
Something like this:
- include_role:
name: role-s3bucket-creator
apply:
delegate_to: localhost
vars:
role_var_name1: "{{ foo }}"
role_var_name2: "{{ bar }}"
Going forward I suggest you ellaborate a little bit more on your questions,
so people can actually understand what are you trying to achieve.
Regards,
On Tue, Aug 24, 2021, 13:50 Tony Wong <[email protected]> wrote:
> i want to reuse the role. i only want to modify the variables for future
> use
>
> On Tuesday, August 24, 2021 at 1:03:10 AM UTC-7 [email protected] wrote:
>
>> Did you read the reply?
>>
>> What do you want to achieve?
>> What is the intention?
>> Why do you say "break this play up into roles/tasks/variables etc."?
>>
>>
>>
>> On Tue, 24 Aug 2021 at 06:01, Tony Wong <[email protected]> wrote:
>> >
>> > my variables are
>> >
>> > ansibletestbucket12345
>> >
>> arn:aws:kms:us-west-1:462518063038:key/f164e76a-f6f8-4773-84dc-053a44b2678d
>> > prod
>> > s3 bucket
>> > util
>> > 32
>> > atomdomain
>> >
>> >
>> >
>> > On Monday, August 23, 2021 at 7:07:36 AM UTC-7 Brian Coca wrote:
>> >>
>> >> you are showing a playbook with a single task and no variables, there
>> >> is not much to break up here
>> >>
>> >> On Fri, Aug 20, 2021 at 4:58 PM Tony Wong <[email protected]> wrote:
>> >> >
>> >> > how do I break this play up into roles/tasks/variables etc....
>> >> >
>> >> >
>> >> > ---
>> >> > - hosts: localhost
>> >> > tasks:
>> >> > - name: create s3 bucket
>> >> > s3_bucket:
>> >> > name: ansibletestbucket12345
>> >> > public_access:
>> >> > block_public_acls: true
>> >> > ignore_public_acls: true
>> >> > block_public_policy: true
>> >> > restrict_public_buckets: true
>> >> > state: present
>> >> > encryption: "aws:kms"
>> >> > encryption_key_id:
>> "arn:aws:kms:us-west-1:462518063038:key/f164e76a-f6f8-4773-84dc-053a44b2678d"
>>
>> >> > region: us-west-1
>> >> > versioning: yes
>> >> > tags:
>> >> > atomenv: prod
>> >> > atomos: s3 bucket
>> >> > atomrole: util
>> >> > atompid: 32
>> >> > atomdomain: xxxxx
>> >> >
>> >> > --
>> >> > You received this message because you are subscribed to the Google
>> Groups "Ansible Project" group.
>> >> > To unsubscribe from this group and stop receiving emails from it,
>> send an email to [email protected].
>> >> > To view this discussion on the web visit
>> https://groups.google.com/d/msgid/ansible-project/eb897354-e82b-4d8e-bdb0-a9fe32f048f0n%40googlegroups.com.
>>
>> >>
>> >>
>> >>
>> >> --
>> >> ----------
>> >> Brian Coca
>> >>
>> > --
>> > You received this message because you are subscribed to the Google
>> Groups "Ansible Project" group.
>> > To unsubscribe from this group and stop receiving emails from it, send
>> an email to [email protected].
>> > To view this discussion on the web visit
>> https://groups.google.com/d/msgid/ansible-project/cd76041a-6d57-493e-97a4-bd1760f8ad7dn%40googlegroups.com.
>>
>>
>>
>>
>> --
>> Dick Visser
>> Trust & Identity Service Operations Manager
>> GÉANT
>>
> --
> You received this message because you are subscribed to the Google Groups
> "Ansible Project" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to [email protected].
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/ansible-project/d273c8b2-58ce-4bc8-a7be-b359d073191cn%40googlegroups.com
> <https://groups.google.com/d/msgid/ansible-project/d273c8b2-58ce-4bc8-a7be-b359d073191cn%40googlegroups.com?utm_medium=email&utm_source=footer>
> .
>
--
You received this message because you are subscribed to the Google Groups
"Ansible Project" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/ansible-project/CAFtje5PAKyzbGo39TyX%2B9y-diTJbNL-Zjikcgqy%3DjNGKDw6NfQ%40mail.gmail.com.
