Mixing
Why aws cli dont invalidate correctly the cache - AWS Cloudfront
I have created a Jenkins job that invalidate the cache each time that my frontend project is deployed. The issue is that although the AWS Website display that the cache is invalidating, when the job finish, the cache isnt completly cleaned, so I need to invalidate it manually through the AWS Website...
The way to invalidate the cache automatically that I used is through aws container where I execute the following command:
aws cloudfront create-invalidation --distribution-id ${DISTRIBUTION_ID} --paths /* > output.json
The output file will contain a json where I can get differents keys: values. Two of they that I use is Id and Status. Once the invalidation was created, I another pipeline step I execute the following:
aws cloudfront get-invalidation --distribution-id ${DISTRIBUTION_ID} --id ${id_invalidator} > status_invalidation.json
With the previously command I quest to the API each 50 second (through a sleep 50) the status of the invalidation. When the validation return a `Status = Completed', the job is finished. This condition are inside a while loop.
Someone know why this is happened?
amazon-web-services jenkins amazon-cloudfront pipeline aws-cli
asked Nov 22 '18 at 13:41
Carlos AndresCarlos Andres
5012716
add a comment |
I have created a Jenkins job that invalidate the cache each time that my frontend project is deployed. The issue is that although the AWS Website display that the cache is invalidating, when the job finish, the cache isnt completly cleaned, so I need to invalidate it manually through the AWS Website...
The way to invalidate the cache automatically that I used is through aws container where I execute the following command:
aws cloudfront create-invalidation --distribution-id ${DISTRIBUTION_ID} --paths /* > output.json
The output file will contain a json where I can get differents keys: values. Two of they that I use is Id and Status. Once the invalidation was created, I another pipeline step I execute the following:
aws cloudfront get-invalidation --distribution-id ${DISTRIBUTION_ID} --id ${id_invalidator} > status_invalidation.json
With the previously command I quest to the API each 50 second (through a sleep 50) the status of the invalidation. When the validation return a `Status = Completed', the job is finished. This condition are inside a while loop.
Someone know why this is happened?
amazon-web-services jenkins amazon-cloudfront pipeline aws-cli
asked Nov 22 '18 at 13:41
Carlos AndresCarlos Andres
5012716
I don't see an issue with the approach you are trying. Were you able to confirm that this is happening only for CLI command and not doing it manually via web console for the first time?
– Ashan
Nov 23 '18 at 2:12
Hi @Ashan ! Thanks for your response. The solution was gived by Michael - sqlbot ! Thanks in all the ways!!
– Carlos Andres
Nov 26 '18 at 1:35
add a comment |
I have created a Jenkins job that invalidate the cache each time that my frontend project is deployed. The issue is that although the AWS Website display that the cache is invalidating, when the job finish, the cache isnt completly cleaned, so I need to invalidate it manually through the AWS Website...
The way to invalidate the cache automatically that I used is through aws container where I execute the following command:
aws cloudfront create-invalidation --distribution-id ${DISTRIBUTION_ID} --paths /* > output.json
The output file will contain a json where I can get differents keys: values. Two of they that I use is Id and Status. Once the invalidation was created, I another pipeline step I execute the following:
aws cloudfront get-invalidation --distribution-id ${DISTRIBUTION_ID} --id ${id_invalidator} > status_invalidation.json
With the previously command I quest to the API each 50 second (through a sleep 50) the status of the invalidation. When the validation return a `Status = Completed', the job is finished. This condition are inside a while loop.
Someone know why this is happened?
amazon-web-services jenkins amazon-cloudfront pipeline aws-cli
asked Nov 22 '18 at 13:41
Carlos AndresCarlos Andres
5012716
I have created a Jenkins job that invalidate the cache each time that my frontend project is deployed. The issue is that although the AWS Website display that the cache is invalidating, when the job finish, the cache isnt completly cleaned, so I need to invalidate it manually through the AWS Website...
The way to invalidate the cache automatically that I used is through aws container where I execute the following command:
aws cloudfront create-invalidation --distribution-id ${DISTRIBUTION_ID} --paths /* > output.json
The output file will contain a json where I can get differents keys: values. Two of they that I use is Id and Status. Once the invalidation was created, I another pipeline step I execute the following:
aws cloudfront get-invalidation --distribution-id ${DISTRIBUTION_ID} --id ${id_invalidator} > status_invalidation.json
With the previously command I quest to the API each 50 second (through a sleep 50) the status of the invalidation. When the validation return a `Status = Completed', the job is finished. This condition are inside a while loop.
Someone know why this is happened?
amazon-web-services jenkins amazon-cloudfront pipeline aws-cli
amazon-web-services jenkins amazon-cloudfront pipeline aws-cli
asked Nov 22 '18 at 13:41
Carlos AndresCarlos Andres
5012716
asked Nov 22 '18 at 13:41
Carlos AndresCarlos Andres
5012716
asked Nov 22 '18 at 13:41
Carlos AndresCarlos Andres
5012716
asked Nov 22 '18 at 13:41
Carlos AndresCarlos Andres
5012716
asked Nov 22 '18 at 13:41
Carlos AndresCarlos Andres
5012716
5012716
I don't see an issue with the approach you are trying. Were you able to confirm that this is happening only for CLI command and not doing it manually via web console for the first time?
– Ashan
Nov 23 '18 at 2:12
Hi @Ashan ! Thanks for your response. The solution was gived by Michael - sqlbot ! Thanks in all the ways!!
– Carlos Andres
Nov 26 '18 at 1:35
add a comment |
I don't see an issue with the approach you are trying. Were you able to confirm that this is happening only for CLI command and not doing it manually via web console for the first time?
– Ashan
Nov 23 '18 at 2:12
Hi @Ashan ! Thanks for your response. The solution was gived by Michael - sqlbot ! Thanks in all the ways!!
– Carlos Andres
Nov 26 '18 at 1:35
I don't see an issue with the approach you are trying. Were you able to confirm that this is happening only for CLI command and not doing it manually via web console for the first time?
– Ashan
Nov 23 '18 at 2:12
I don't see an issue with the approach you are trying. Were you able to confirm that this is happening only for CLI command and not doing it manually via web console for the first time?
– Ashan
Nov 23 '18 at 2:12
Hi @Ashan ! Thanks for your response. The solution was gived by Michael - sqlbot ! Thanks in all the ways!!
– Carlos Andres
Nov 26 '18 at 1:35
Hi @Ashan ! Thanks for your response. The solution was gived by Michael - sqlbot ! Thanks in all the ways!!
– Carlos Andres
Nov 26 '18 at 1:35
add a comment |
1 Answer
1
active
oldest
votes
You always have to quote expressions with the * character on the command line, to avoid local shell expansion. The correct syntax is this:
--paths '/*'
Otherwise you are trying to invalidate names based on what's in the root directory on your local filesystem (as captured by the *, expanded by the shell).
answered Nov 23 '18 at 2:19
Michael - sqlbotMichael - sqlbot
92.8k13137199
add a comment |
Your Answer
StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53432292%2fwhy-aws-cli-dont-invalidate-correctly-the-cache-aws-cloudfront%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
You always have to quote expressions with the * character on the command line, to avoid local shell expansion. The correct syntax is this:
--paths '/*'
Otherwise you are trying to invalidate names based on what's in the root directory on your local filesystem (as captured by the *, expanded by the shell).
answered Nov 23 '18 at 2:19
Michael - sqlbotMichael - sqlbot
92.8k13137199
add a comment |
You always have to quote expressions with the * character on the command line, to avoid local shell expansion. The correct syntax is this:
--paths '/*'
Otherwise you are trying to invalidate names based on what's in the root directory on your local filesystem (as captured by the *, expanded by the shell).
answered Nov 23 '18 at 2:19
Michael - sqlbotMichael - sqlbot
92.8k13137199
add a comment |
You always have to quote expressions with the * character on the command line, to avoid local shell expansion. The correct syntax is this:
--paths '/*'
Otherwise you are trying to invalidate names based on what's in the root directory on your local filesystem (as captured by the *, expanded by the shell).
answered Nov 23 '18 at 2:19
Michael - sqlbotMichael - sqlbot
92.8k13137199
You always have to quote expressions with the * character on the command line, to avoid local shell expansion. The correct syntax is this:
--paths '/*'
Otherwise you are trying to invalidate names based on what's in the root directory on your local filesystem (as captured by the *, expanded by the shell).
answered Nov 23 '18 at 2:19
Michael - sqlbotMichael - sqlbot
92.8k13137199
answered Nov 23 '18 at 2:19
Michael - sqlbotMichael - sqlbot
92.8k13137199
answered Nov 23 '18 at 2:19
Michael - sqlbotMichael - sqlbot
92.8k13137199
answered Nov 23 '18 at 2:19
Michael - sqlbotMichael - sqlbot
92.8k13137199
92.8k13137199
add a comment |
add a comment |
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53432292%2fwhy-aws-cli-dont-invalidate-correctly-the-cache-aws-cloudfront%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
I don't see an issue with the approach you are trying. Were you able to confirm that this is happening only for CLI command and not doing it manually via web console for the first time?
– Ashan
Nov 23 '18 at 2:12
Hi @Ashan ! Thanks for your response. The solution was gived by Michael - sqlbot ! Thanks in all the ways!!
– Carlos Andres
Nov 26 '18 at 1:35