Thursday, November 18, 2021
AWS: Cloudformation : How to update Stack by a new resource
LEARN From Here -> https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/gettingstarted.templatebasics.html
https://aws.amazon.com/premiumsupport/knowledge-center/cloudformation-custom-name/
https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/using-cfn-updating-stacks.html
https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/cfn-whatis-howdoesitwork.html
https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-template-resource-type-ref.html
Update requires: No interruption
docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/using-cfn-updating-stacks-get-template.html#using-cfn-updating-stacks-get-stack.CON
When updating a stack, AWS CloudFormation might interrupt resources or replace updated resources, depending on which properties you update. For more information about resource update behaviors, see Update behaviors of stack resources.
Update methods
AWS CloudFormation provides two methods for updating stacks: direct update or creating and executing change sets. When you directly update a stack, you submit changes and AWS CloudFormation immediately deploys them. Use direct updates when you want to quickly deploy your updates.
With change sets, you can preview the changes AWS CloudFormation will make to your stack, and then decide whether to apply those changes. Change sets are JSON-formatted documents that summarize the changes AWS CloudFormation will make to a stack. Use change sets when you want to ensure that AWS CloudFormation doesn't make unintentional changes or when you want to consider several options. For example, you can use a change set to verify that AWS CloudFormation won't replace your stack's database instances during an update.
Drift detection operations
Tuesday, November 16, 2021
Monday, November 15, 2021
AWS : Cloudformation : Create LoadBalancer and Domains
docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/parameters-section-structure.html
https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/quickref-route53.html
https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/quickref-elb.html
https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-properties-resource-tags.html
- AWS Docs
- AWS User-Guide-Quick Reference
aws cloudformation create-stack --stack-name cca-cloudformation-targetgroup --template-url s3://cca-cloudformation-template/CCA-CloudFormationTemplate-TargetGroup.json --parameters s3://cca-cloudformation-template/params.json
aws cloudformation create-stack --stack-name cca-cloudformation-targetgroup --template-body file://CCA-CloudFormationTemplate-TargetGroup.json --parameters file://params.json
Sunday, November 14, 2021
Azure : Mount Azure Storage Blob in Linux Folder : BlobFuse
https://docs.microsoft.com/en-us/azure/storage/blobs/storage-how-to-mount-container-linux
Warning
Blobfuse doesn't guarantee 100% POSIX compliance as it simply translates requests into Blob REST APIs.
Install blobfuse
Configure your storage account credentials
Mount
Valid authentication setups:
- Account Name & Key (
authType Key
)- Requires the accountName, accountKey and containerName specified in the config file or command line.
- Alternatively accountName and accountKey can be specified by the following environment values instead: AZURE_STORAGE_ACCOUNT, AZURE_STORAGE_ACCESS_KEY.
- Account Name & SAS (
authType SAS
)- Requires the accountName, containerName and sasToken specified in the config file or command line.
- Alternatively accountName can be specified by the environment values AZURE_STORAGE_ACCOUNT
- Managed Identity (
authType MSI
)- Single assigned identity:
- No extra parameters needed.
- Multiple assigned identities:
- At least one of the following for the intended identity:
- Client ID (Use this if you are using a custom Managed Identity endpoint)
- Object ID
- Resource ID
- At least one of the following for the intended identity:
- Add Storage Blob Data Contributor roles to this identity in the Storage account.
- Single assigned identity:
- Service Principal Name (
authType SPN
)- Requires servicePrincipalClientId, servicePrincipalTenantId, servicePrincipalClientSecret specified in the config file.
- Alternatively servicePrincipalClientSecret can be specified by the environment value AZURE_STORAGE_SPN_CLIENT_SECRET
- AZURE_STORAGE_AAD_ENDPOINT`environment value can be used to specify a custom AAD endpoint to authenticate against
- Add Storage Blob Data Contributor roles to this identity in the Storage account.
Azure - Pipeline - Add Approver for Stage
https://learn.microsoft.com/en-us/azure/devops/pipelines/process/approvals?view=azure-devops&tabs=check-pass
-
https://www.baeldung.com/spring-properties-file-outside-jar https://docs.spring.io/spring-boot/docs/current/reference/html/spring-boot-featu...
-
https://learn.microsoft.com/en-us/azure/devops/pipelines/process/approvals?view=azure-devops&tabs=check-pass
-
The decision was made to block such external HTTP repositories by default https://stackoverflow.com/questions/66980047/maven-build-failure-d...