Skip to main content

Start Here If You Are Not Technical

You do not need to know the cloud, the syntax or Git to ask for a change. You need to know the result that you want. Beck, the Infrastream assistant, does the technical part. A colleague with merge rights completes the change.

In short
  • You ask Beck in plain words, in the Infrastream portal.
  • Beck writes the change and shows a plan of what will change.
  • You read the summary. If it is wrong, tell Beck.
  • A person merges the change. The engine applies what you merge.

From a sentence to a live app​

  1. Open the Beck chat in the Infrastream portal.
  2. Describe the result that you want, in your own words.
  3. Beck opens a pull request. A pull request is a written change that you can read before it applies. It shows a plan of what will change.
  4. Read the summary. Ask yourself: does this do what I asked? If not, tell Beck what to change.
  5. Ask a colleague with merge rights to read the pull request and merge it.
  6. The platform applies the change. Your app, bucket or setting appears.

A new version of an existing app takes another path. The release track moves the version from stage to stage. A stage can require approval from a named group. See The Agent Path.

Who does what​

WhoWhat they do
YouAsk for the result. Check that the summary matches what you asked.
BeckWrites the change, opens the pull request and answers questions.
A mergerA colleague with merge rights. Reads the pull request and merges it.
An approverA member of a named group. Says yes when a release stage needs approval.
An administratorSets who can reach what. See Govern People and Their Agents.

Your branch rules decide who can merge. Ask your team lead who your mergers are.

What to ask​

Say what you want. Do not worry about the words. These are examples.

  • "Make the expense tracker open only to the finance group."
  • "Put the quote calculator online for anyone to use."
  • "Which apps use the payments database?"
  • "List any buckets that grant public access."
  • "Why did my app not start?"

If a word is new, ask Beck. For example, ask, "What is a release stage?"

What you cannot break​

WorryThe fact
"I asked for the wrong thing."The engine applies what a person merges. Close the pull request, or ask Beck for a new one.
"I changed a setting by mistake."A pull request that reverts the commit puts the setting back.
"I removed something that held data."Settings revert. Deleted data does not. A database that you remove and then restore comes back empty.
"I will open a door to the internet."The network is default-deny. Each project lists the outside sites that its apps can call.
"I will see a secret."No tier can read a secret payload, change IAM or impersonate a service account.
"The bill will grow."Apps scale to zero when nobody uses them. A fixed base stays on: the gateway, the network, the server of the assistant and any database.

Words you will see​

WordIn plain words
ManifestA short, typed file that says what you will get. Your team reads the same file.
Pull requestA written change that you can read before it applies.
PlanThe list of what a change will add, change or remove.
EnvironmentA place where an app runs, such as development, staging or production.
Release stageA step that a new version of an app passes on its way to production.
TierWhat a person can do in a project: read, dev or admin.
ApproverA person in a named group who must say yes before a release stage continues.

If you get stuck​

  • Ask Beck. Say what you tried and what you see.
  • Ask your team lead to add you to the group of your team. You get access through groups.
  • To learn more, read Get Started and Use Beck.

Next​