1a8e

### Keybase proof

I hereby claim:

  * I am psiyan on github.
  * I am psiyan (https://keybase.io/psiyan) on keybase.
  * I have a public key ASC8q3RKpG7bK3U1C2gqrm9vJoWlZ5801VhFVY-vTT46VAo

To claim this, I am signing this object:

1a8e

Tech Documentation for API to update the KFC menu items for the provided store_id on-demand.

• API Schematics

  • REQUEST METHOD: POST

  • REQUEST URL: BASE_HAPTIK_URL + /integration/update_kfc_store_menu/

  • REQUEST HEADERS:

1a8e

Keybase proof

I hereby claim:

• I am psiyan on github.
• I am psiyan (https://keybase.io/psiyan) on keybase.
• I have a public key ASBMPYY5gYxQtQ34enaZWMIg22hN5_Mr1fkRumn0EH9H-Qo

To claim this, I am signing this object:

1a8e

Keybase proof

I hereby claim:

• I am 1a8e on github.
• I am psiyan (https://keybase.io/psiyan) on keybase.
• I have a public key ASBMPYY5gYxQtQ34enaZWMIg22hN5_Mr1fkRumn0EH9H-Qo

To claim this, I am signing this object:

1a8e

The container and the submodule truly act as independent repos.

What?

Submodules, like subtrees, aim to reuse code from another repo somewhere inside your own repo’s tree. The module has its own repo, somewhere inside the working directory of its container repo. At deployment, a specific commit hash is pulled into the larger repositiory and deployed.

Makes working on extensions by ISVs similar to application development where they are exposed an API.

1a8e

ssh-ed25519 AAAAC3NzaC1lZDI1NTE5AAAAINJ8zzhJzfbLuwl1YxqbyU1S5qzB0b6Bh14/2zwAsCXK 1a8e