Bash completion script for curl for exploring internal instance (169.254.169.254) API on AWS and GCP

_curl_api

# curl metadata api explorer                   -*- shell-script -*-
# you can copy paste it inside ~/.bash_completion

_curl_api()
{
    local cur prev word cword
    _init_completion -n : || return

    case "$cur" in

    http://169.254.169.254/*)
        POS=$((`echo $cur | grep -aob '/' | grep -oE '^[0-9]+' | tail -n1` + 1 ))
        _metadata=`curl -f -s "${cur:0:$POS}"`
        if [[ ! -z "$_metadata" ]]; then
            args=""
            for i in $_metadata; do
                if [[ "${i: -1}" != "/" && -z `curl -f -s "${cur:0:$POS}$i"` ]]; then i=$i"/"; fi
                args="$args ${cur:0:$POS}$i"
            done
            args="${args:1}"
            COMPREPLY=( $( compgen -W "$args" -- "$cur" ) )
          # Work-around bash_completion issue where bash interprets a colon as a separator.
          # Work-around borrowed from the darcs work-around for the same issue.
          local colonprefixes=${cur%"${cur##*:}"}
          local i=${#COMPREPLY[*]}
          while [ $((--i)) -ge 0 ]; do
            COMPREPLY[$i]=${COMPREPLY[$i]#"$colonprefixes"}
          done
          compopt -o nospace
        fi
        return
        ;;

    h*)
       COMPREPLY=( $( compgen -W 'http://169.254.169.254/' -- "$cur" ) )
          # Work-around bash_completion issue where bash interprets a colon as a separator.
          # Work-around borrowed from the darcs work-around for the same issue.
          local colonprefixes=${cur%"${cur##*:}"}
          local i=${#COMPREPLY[*]}
          while [ $((--i)) -ge 0 ]; do
            COMPREPLY[$i]=${COMPREPLY[$i]#"$colonprefixes"}
          done
          compopt -o nospace
          return
          ;;
    esac

} &&
complete -F _curl_api curl