How to apply data retention policy on already created storage container - azure-storage-account

Closed. This question is opinion-based. It is not currently accepting answers.
Update the question so it can be answered with facts and citations. This will help others answer the question. You can edit the question or post a new one.
Closed 16 hours ago.
We are in the final phase of our project and would like to know the understanding for below questions.
We would like to set up a retention policy which is applicable for all folders/subfolders and files inside the container. The storage account is already setup but without the retention policy. Can we apply the retention policy after creating the storage container? How we can do this?
How to apply retention policy only for few folders not all. How we can achieve this?
How we can import the .bacpac file into UAT and production with an existing database?
Thanks, Sachin

Related

Why do we need Docker? [closed]

Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 12 months ago.
Improve this question
I need a detailed answer to explain
importance of docker
need of Docker , why are we using docker
how Docker plays an important role in the field of development and Deployment .
Top benefits are:
isolation of the environment
easy to test out new software/technologies without any effort to install them
deployments are very fast
integrates great with the concept of micro services
popularity
there is a lot of useful images, that can be used, by a lot of companies
There is also a lot of good articles, that you can find, when you type something like "docker biggest benefits" in google.

Is Jenkins safe to use? [closed]

Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 1 year ago.
Improve this question
So for a schoolproject we want to use Jenkins. During the installation, Jenkins asks for service logon credentials (local/ domain accountname and the password for the account). This raised a question in the group wether Jenkins is safe to use or not, because you are giving away sensitive information.
So is Jenkins safe to use? Could somebody also give a explanation why it is safe to use (How it works exactly)
Read Securing Jenkins
Create a service account (needs logonasservice) as explained here for the controller.
Have a separate account to run the agents under. Use a third to access the source control system (use credentials plugin).
Your admins can restrict where the accounts can run and what privileges the have. Do NOT run as system or root (inside Docker is OK) and it's fine.

JIRA service Desk Test environment [closed]

Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 5 years ago.
Improve this question
We are using JIRA Software and JIRA Service Desks in our company.
I am new to JIRA and i want to ask if it is possible to create a test environment for a few projects or service desks? If yes, how can i set it up ?
Mfg
Technically, JIRA ServiceDesk is a Plugin in JIRA and it uses AO Tables. With that said, JIRA Project Export and Import doesn't support Exporting AO Tables. It means that you are not able to import ServiceDesk Projects to the other instances. You can take a look at their feature request here.
Thus, I would say it's better to clone the full production instance into a test environment. In order to do that, you have to create backup from home directory, installation directory and database and restore them into a test instance. Full steps are available here in Atlassian Documentations.
Please note that, prior to start the staging environment you have to disable incoming and outgoing emails with the available JVM Arguments. Otherwise, new issues will create in your test servers instead of production.

Far future expiration date [closed]

Closed. This question needs details or clarity. It is not currently accepting answers.
Want to improve this question? Add details and clarify the problem by editing this post.
Closed 8 years ago.
Improve this question
How can i mention far future expiration date for google ad services, google analytics...
These are some things shown in gtmetrix site for yslow.
i am using nginx server
http://www.googleadservices.com/pagead/conversion.js
http://www.google-analytics.com/analytics.js
http://storage.googleapis.com/code.snapengage.com/js/cb502944-bd87-448a-b7e3-34353b0136c7.js
https://commondatastorage.googleapis.com/code.snapengage.com/btn/livechat_right_en.png
how can i add future expiration date for these links.
Assuming you are talking about the Cache expiration date, the answer as Alexey Ten is "you can't".
Those resources are not controlled by you, nor on your servers. They are loaded by the browsers from external servers, therefore you have no control over them. The expiration header is set by the server that serves the asset.
In some cases you can proxy the resource (aka put a custom layer between the resource and the client), so that you can configure the cache via the proxy. But I'm not sure in this case it's a recommendable option.

What thing should be excluded when posting an open-source project on GitHub [closed]

Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 9 years ago.
Improve this question
I would like to add an open-source, ruby-on-rails project to GitHub. I would like to make it as easy as possible for others to contribute, while protecting sensitive information.
In addition to:
database passwords
API keys
Which things are best suited to environment variable (e.g. ENV['MY_API_KEY'])?
In addition to:
config/database.yml (thanks house9)
Which things are best included in the .gitignore file?
What gems or other tools are helpful in this regard?
Should sensitive accounts (e.g. 'admin') be created directly in the database in the production environment?
I would put config/database.yml in .gitignore and have a config/database.yml.example file for people to use
consider using dotenv
https://rubygems.org/gems/dotenv-rails
https://github.com/bkeepers/dotenv
the default .env file can have 'stubbed' out values that will at least let someone fire it up in development and then it can be replaced when deploying with actual values

Resources